perf: use Python 3.14#378
Open
bolinocroustibat wants to merge 7 commits intomainfrom
Open
Conversation
bolinocroustibat
force-pushed
the
python-3.14
branch
from
5effabf to
b0d9160
Compare
bolinocroustibat
force-pushed
the
python-3.14
branch
2 times, most recently
from
1b2a234 to
6f34388
Compare
# Conflicts: # uv.lock
# Conflicts: # uv.lock
bolinocroustibat
force-pushed
the
python-3.14
branch
2 times, most recently
from
68929ce to
af22889
Compare
bolinocroustibat
force-pushed
the
python-3.14
branch
from
af22889 to
ee67386
Compare
Pierlou
approved these changes
Mar 6, 2026
Contributor
Pierlou
left a comment
Pierlou
left a comment
There was a problem hiding this comment.
Well that was an easy review, thanks for the upgrade! We can try this on dev/demo ⚡
# Conflicts: # uv.lock
Contributor
Author
Waiting for the infra to be adapted to Python 3.14 first to be able to deploy, either by installing it on Debian (Debian Trixie ships Python 3.13 by default, not 3.14) and recreating a venv, either by refactoring the infra playbook to install Hydra via uv along the right Python version - @jordanguedj is on it |
# Conflicts: # uv.lock
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrading from Python 3.11 to 3.14 for performance gains on our pure-Python workloads.
Benchmark results (circleci, same runner, 4 runs for Python 3.14)
Results from the benchmarks branch. The PMTiles test acts as a negative control (C++ tool, unaffected by Python version), confirming the CSV gains might be real.
The 4 Python 3.14 runs are consistent: 28.41s, 29.23s, 28.49s, 30.51s (standard deviation of 0.97s).
A single 3.13 run on a different runner showed no improvement over 3.11 — not conclusive given the different setup, but it hints the gains may be specific to 3.14 which is consistent with what we can read on some performance reports.
The speedup could come from Python 3.14's interpreter improvements, which benefit
csv-detectiveanddateparser(pure-Python workloads)?